…#4)

## Rationale

The Record Treatment link on study.treatment_order passed the order's
start date as the scheduledDate URL parameter, so every treatment
recorded through it carried the same scheduledDate regardless of which
schedule slot was being recorded. The second recording against an order
then tripped the duplicate-treatment trigger in study/drug.js ("A
treatment has already been entered for this order for this date and
time.") while the treatmentSchedule grid still showed the slot as
unrecorded, since its status join compares the computed slot time
against the stored scheduledDate.

## Related Pull Requests

- LabKey/johnsHopkinsEHRModules#667 (same fix
for jhu_ehr)
- LabKey/nircEHRModules#730 (same fix for
nirc_ehr)

## Changes

- Extract the inline Record Treatment display column into
TreatmentDisplayColumnFactory with an includeScheduledDate flag; emit
scheduledDate only when set, ISO-formatted via
DateUtil.formatIsoDateShortTime() instead of Date.toString(); add a null
guard on category.
- The treatment_order Record Treatment link no longer passes
scheduledDate; new customizeTreatmentSchedule() adds a treatmentRecord
link column to study.treatmentSchedule that passes the slot's date.
- treatmentSchedule.sql: drop the t1.treatmentRecord passthrough column
inherited from treatment_order.
- treatmentSchedule.query.xml: apply the module customizer via
javaCustomizer so the new column is added.